Touch screen for convergence and automation system

ABSTRACT

An automation system operating in a Web Service for Devices environment includes clients and devices, a network comprising a server configured to be connected to the clients and devices with the web services for devices, and a touch screen device coupled to the network and provided a user interface for controlling the devices. The clients and devices are configured with a web services for devices stack protocol to provide automation-based control and communication between the clients and devices.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to and the benefit of ProvisionalPatent Application No. 60/793,257 filed on Apr. 20, 2006, entitled TOUCHSCREEN FOR USE WITH AUTOMATION SYSTEMS, to Seale MOORER, et al., whichis hereby expressly incorporated by reference for all purposes as iffully set forth herein.

Further, this application is related to the following U.S. patentapplications: U.S. patent application Ser. No. 11/686,826, entitledNETWORK BASED DIGITAL ACCESS POINT DEVICE, filed Mar. 15, 2007, to SealeMoorer, et al., having Attorney Docket No.: 2047672-5013US; U.S. patentapplication Ser. No. 11/686,836, entitled INTERNET PROTOCOL BASED MEDIASTREAMING SOLUTION, filed Mar. 15, 2007, to Seale Moorer, et al., havingAttorney Docket No.: 2047672-5014US; U.S. patent application Ser. No.11/686,896, entitled AUTOMATION CONTROL SYSTEM HAVING A CONFIGURATIONTOOL AND TWO-WAY ETHERNET COMMUNICATION FOR WEB SERVICE MESSAGING,DISCOVERY, DESCRIPTION, AND EVENTING THAT IS CONTROLLABLE WITH ATOUCH-SCREEN DISPLAY, filed Mar. 15, 2007, to Seale Moorer, et al.,having Attorney Docket No.: 2047672-5017US; U.S. patent application Ser.No. 11/686,884, entitled AUTOMATION CONTROL SYSTEM HAVING DIGITALLOGGING, filed Mar. 15, 2007, to Seale Moorer, et al., having AttorneyDocket No.: 2047672-5018US; U.S. patent application Ser. No. 11/686,893,entitled USER CONTROL INTERFACE FOR CONVERGENCE AND AUTOMATION SYSTEM,filed Mar. 15, 2007, to Seale Moorer, et al., having Attorney DocketNo.: 2047672-5019US; U.S. patent application Ser. No. 11/686,846,entitled DEVICE AUTOMATION USING NETWORKED DEVICE CONTROL HAVING A WEBSERVICES FOR DEVICES STACK, filed Mar. 15, 2007, to Seale Moorer, etal., having Attorney Docket No.: 2047672-5020US; U.S. patent applicationSer. No. 11/686,875, entitled AUTOMATION CONTROL SYSTEM HAVING ACONFIGURATION TOOL, filed Mar. 15, 2007, to Seale Moorer, et al., havingAttorney Docket No.: 2047672-5022US; and U.S. patent application Ser.No. 11/686,889, entitled AUTOMATION CONTROL SYSTEM HAVING DEVICESCRIPTING, filed Mar. 15, 2007, to Seale Moorer, et al., having AttorneyDocket No.: 2047672-5023US; which are all hereby expressly incorporatedby reference for all purposes as if fully set forth herein.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The invention is directed to multiple device control and convergencethat includes a touch screen device, and more particularly to multipledevice addressing, discovery, description, control, eventing, andconvergence in a Web Service environment, and control through a touchscreen input device.

2. Related Art

Household, academic and/or business spaces now more commonly have morethan one audio or video device such as CD/DVD player, portable MP3player, tuner, preamp, power amp, speakers, VCR, DVR, computers runningmedia players or connected to some other source of audio or video (e.g.,Internet radio, satellite radio and the like), set top boxes (STB), etc.Typically, a CD/DVD player from one company comes with its own remotecontrol and an amplifier by an entirely different company comes with itsown remote control. The same space may have a PC with its keyboard andmouse, and yet another company's portable MP3 player with its owncontrol switches. The same space may include cable-enabled devices suchas set top boxes providing television signals and the like. While eachaudio/video device is doing precisely what it was designed to do, eachoperates completely independent from the others with the possibleexception of the portable MP3 player that may be connected to a PC forsynchronization. As a result, a user ends up going from one keypad toanother or juggling a series of remote controls in order to control thedevices.

Since these audio/video and similar devices are not designed tocommunicate with each other or their communication is very limited,access to these audio/video devices is limited by their physicallocations. For example, it is difficult to play a digital audio files(such as MP3, WMA, etc.) saved in a PC hard disk drive in one room orarea (a child's bedroom) on speakers located in another room or area (anentertainment room). Thus, in order for a user to enjoy music of his orher choice whenever and wherever he or she wants, each room needs to beequipped with all the necessary audio/video equipment and digitalaudio/video content.

Also, the audio/video devices are not designed to communicate with otherdevices (e.g., TV, lighting, security system, etc.). Thus, it isdifficult, if not impossible, to converge the devices for common controlfor certain occasions. For example, in order to watch a movie, the usermust turn on a TV, a DVD player and an audio amplifier by using threedifferent remote controls. Then the user must set the TV to receive avideo signal from the DVD player, set the audio amplifier to receive anaudio signal from the DVD player and use another control unit to adjustthe lighting of the room. Even when a user utilizes a universal remote,as is known in the art, the result is a plurality of devices that areseparately operated and are operated separately from a single universalremote. These devices do not converge as described above because thedevices lack any ability to easily connect and effectively communicatewith each other, and be controlled by a single input device.

Accordingly, there is a need for a solution for the aforementionedaccessibility, connectability and convergence issues to allow devices toconnect, communicate and be controlled.

SUMMARY OF THE INVENTION

The invention meets the foregoing needs using an automation specific IPbased automation protocol, which results in a significant increase indiscovery and communications between devices along with an IP basedinput device and other advantages apparent from the discussion herein.

Accordingly, in one aspect of the invention, a process of operating anautomation system in a Web Service environment includes providing atleast one client and at least one device, the at least one client andthe at least one device configured with a web services for devices stackprotocol, connecting a network comprising at least one server with theweb services for devices to the at least one client and the at least onedevice, connecting a touch screen device as another at least one clientto the network, the touch screen device implemented with a userinterface for controlling the at least one device, and transmittingautomation-based control and communication between the at least oneclient and at least one device, wherein the at least one devicecomprises one of an audio system, a video system, an intercom system, alighting system, a security system, a link, and a HVAC system.

The at least one client may include one of a TV, a personal computer, apersonal digital assistant, and a game controller. The process mayfurther include receiving a user input to the touch screen devicethrough at least one of hotspot arranged on a front surface of a touchscreen housing configured to activate a predetermined function uponbeing touched and at least one slider area arranged on an edge portionof the housing configured to provide increasing or decreasing activationof a predetermined function responsive to a sliding touch. The processmay further include generating audio from the touch screen device withat least one speaker. The process may further include at least one ofreceiving IR input to the touch screen device through an IR receiver andsensing light in the touch screen device with a photocell sensor. Theweb services for devices stack may include a services tier that providescommunication via at least one of HTTP and UDP wherein the communicationvia HTTP and UDP comprises information contained in SOAP packets, and alogical interface with the at least one client, and the web services fordevices stack protocol comprises a web service for each at least onedevice, wherein the web services for devices stack protocol may includea service provider configured as a generic host for web services. Theweb services for devices stack protocol may further include one of acomponent configured to host multiple services, and a controllerconfigured to communicate with the at least one device and wherein theweb services for devices stack protocol further comprises a devicebridge configured to translate commands for the devices.

Accordingly, in another aspect of the invention, a machine-readablemedium includes instructions stored therewith, which, when executed by aprocessor cause the processor to establish an automation system in a WebService environment. The machine-reachable medium includes instructionsfor providing automation-based control and communication between atleast one client and at least one device, the at least one client andthe at least one device configured with a web services for devices stackprotocol configured to the at least one client and at least one device,instructions for configuring a network comprising at least one server tobe connected to the at least one client and the at least one device withthe web services for devices, and instructions for coupling a touchscreen device as another at least one client to the network andconfigured to provide the touch screen device coupled thereto with auser interface for controlling the devices, wherein the at least onedevice may include an audio system, a video system, an intercom system,a lighting system, a security system, a link, and a HVAC system.

The at least one client may include one of a TV, a personal computer, apersonal digital assistant, and a game controller. The machine-readablemedium may further include instructions for generating audio from thetouch screen device with at least one speaker. The machine-readablemedium may further include instructions for receiving IR input to thetouch screen device through an IR receiver. The machine-readable mediummay further include instructions for sensing light in the touch screendevice with a photocell sensor. The web services for devices stackprotocol may include a services tier that provides communication via atleast one of HTTP and UDP wherein the communication via HTTP and UDPcomprises information contained in SOAP packets, and a logical interfacewith the at least one client, and the web services for devices stackprotocol comprises a web service for each at least one device. Thecontroller may be configured to send feedback from the at least onedevice to the at least one client.

Accordingly, in another aspect of the invention, an automation systemoperating in a Web Service for Devices environment includes at least oneclient and at least one device, the at least one client and the at leastone device configured with a web services for devices stack protocolconfigured to provide automation-based control and communication betweenthe at least one client and at least one device, a network comprising atleast one server configured to be connected to the at least one clientand the at least one device with the web services for devices, and atouch screen device coupled to the network as another at least oneclient to provide a user interface to control the at least one device,wherein the at least one client further comprises one of a TV, apersonal computer, a personal digital assistant, and a game controllerand the at least one device comprises an audio system, a video system,an intercom system, a lighting system, a security system, a link, and aHVAC system.

The touch screen device may include a display panel, a housing holdingthe display panel and a rear compartment arranged on a rear surface ofthe display panel and containing components for driving the displaypanel. The housing may include at least one hotspot arranged on a frontsurface of the housing configured to activate a predetermined functionupon being pushed, and at least one slider area arranged on an edgeportion of the housing configured to provide increasing or decreasingactivation of a predetermined function. The touch screen device mayfurther include at least one speaker. The touch screen device furthermay further include an IR receiver. The touch screen device may furtherinclude a photocell sensor.

Additional features of the invention may be set forth or apparent fromconsideration of the following detailed description, drawings, andclaims. Moreover, it is to be understood that both the foregoing summaryof the invention and the following detailed description are exemplaryand intended to provide further explanation without limiting the scopeof the invention as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention, are incorporated in and constitute apart of this specification, illustrate embodiments of the invention andtogether with the detailed description serve to explain the principlesof the invention. No attempt is made to show structural details of theinvention in more detail than may be necessary for a fundamentalunderstanding of the invention and the various ways in which it may bepracticed. In the drawings:

FIG. 1 shows an schematic overview of a convergence and automationsolution constructed according to the principles of the invention;

FIG. 2 schematically shows the web services for devices stack for use inthe convergence and automation solution of FIG. 1, constructed accordingto principles of the invention;

FIG. 3 shows a device life cycle operating according to the principlesof the invention;

FIG. 4 shows a schematic overview of the convergence and automationsolution of FIG. 1 implemented with a touch screen;

FIGS. 5A and 5B show front and side perspective views of the touchscreen of FIG. 4, constructed according to principles of the invention;

FIG. 6 shows hot spots and slide areas implemented in the touch screenof FIGS. 5A and 5B;

FIGS. 7A, 7B and 7C show screen capture images of the touch screen ofFIG. 6 displaying weather-related information;

FIGS. 8A and 8B show screen capture images of the touch screen of FIG. 6displaying lighting-related information;

FIGS. 9A, 9B and 9C show screen capture image of the touch screen ofFIG. 6 displaying media-related information; and

FIGS. 10A, 10B and 10C show screen capture image of the touch screen ofFIG. 6 displaying security, camera and shade related information.

DETAILED DESCRIPTION OF THE INVENTION

The embodiments of the invention and the various features andadvantageous details thereof are explained more fully with reference tothe non-limiting embodiments and examples that are described and/orillustrated in the accompanying drawings and detailed in the followingdescription. It should be noted that the features illustrated in thedrawings are not necessarily drawn to scale, and features of oneembodiment may be employed with other embodiments as the skilled artisanwould recognize, even if not explicitly stated herein. Descriptions ofwell-known components and processing techniques may be omitted so as tonot unnecessarily obscure the embodiments of the invention. The examplesused herein are intended merely to facilitate an understanding of waysin which the invention may be practiced and to further enable those ofskill in the art to practice the embodiments of the invention.Accordingly, the examples and embodiments herein should not be construedas limiting the scope of the invention, which is defined solely by theappended claims and applicable law. Moreover, it is noted that likereference numerals represent similar parts throughout the several viewsof the drawings.

FIG. 1 schematically shows an overview of a convergence solutionaccording to an embodiment of the invention. The convergence solutionmay be a combination of hardware and software. The hardware may includea server 10 connected to a network 12 (e.g. IP based wired or wirelessnetwork such as an Ethernet network) and may possibly be connected tothe internet 14, devices 102 (e.g. audio 20, video 22 (e.g., STB),intercom 24, lighting 26, security system 28, HVAC 38, and the like) andclients 104 (e.g. TV 30, personal computer (PC) 32, personal digitalassistance (PDA) 34, controller 36 such as a control panel, gamecontroller (i.e. X-Box™, not shown) and the like). Moreover, the clients104 may include a remote control 39 or a remote control may beconfigured to be a client 104. The server 10 may be any type ofcomputer, such as a PC connected to the network 12. The clients 104 suchas clients 30, 32, 34, 36 may provide a user with control over thedevices 102 such as devices 20, 22, 24, 26, 28, 38.

FIG. 1 further schematically shows interaction of the convergence asolution interacting with non-internet protocol devices such asnon-internet protocol devices 52, 56. Non-internet protocol device 52(non-IP) device is considered non-internet protocol in that it does notinclude a communications interface that is IP based. The non-IP device52 may include other types of (serial, COM port, and the like)communication protocols. Accordingly, the server 10 may be configured toinclude various inputs and outputs to provide communication and controlto various devices such as non-IP device 52. Non-IP device 52 may beimplemented as any number of different devices including, for exampleonly, window shade automation devices, audio devices, video devices andso on.

FIG. 1 further shows implementation of the convergence solution that maycommunicate with a non-IP device such as the non-IP device 56 that notarranged proximate to server 10. In order to accomplish communicationbetween the non-IP device 56 and the network 12, a link or conversionmodule 54 may be arranged in communication with the network 12. Theconversion module 54 connects to the network with an Ethernet typeconnection that provides internet protocol communications with thenetwork 12. The conversion module 54 further provides a second type ofcommunication connection as shown by 58 that may be any type ofcommunication protocol as noted above with respect to communicationprotocol 60. Accordingly the non-IP device 56 may then communicate vianetwork 12 and operate as a web service device accordingly.

The software (i.e., application) enables the hardware such as the server10, devices 102, and clients 104 to communicate with each other despitetheir different proprietary languages and communication protocols, andmay provide the user with control over most or all the hardware from asingle client. The application may utilize at least one portion of thehardware to send commands to the devices 102 and receive feedback fromthem. The application may integrate centralized device control into a PCbased media environment (e.g., Microsoft Media Center™ environment) thatmay store, organize and play digital media content. The user may use thesame remote control 39 to listen to music, watch and record television,enjoy family photographs and home movies, as well as adjust thelighting, secure the home, adjust the temperature, distribute musicthroughout the house, check surveillance cameras and the like.

The application may be implemented with Web Services. The Web Servicesuse standard Internet protocol (IP) and are based on standardXML-related technologies such as SOAP (Simple Object Access Protocol)for communications and WSDL (Web Services Device Language) to describeinterfaces. The devices implemented with Web Service for Device (WSD)become black boxes on the network, providing services to anyapplication, on any platform, written in any language.

Alternatively or additionally, if the server 10 or the PC 32 is runninga SideShow™ enabled operating system such as Microsoft Windows Vista™,the devices may be configured as a SideShow™ device or “gadget.” ASideShow™ device or gadget may communicate with any client or deviceimplemented with WSD in the network via protocols according to SideShow™XML communication specifications. Moreover, the server 10 or the PC 32using Microsoft Windows Vista™ may be running a SideShow™ gadgetapplication running on the Microsoft Windows Vista™ computer providing auser interface rendering for the device that communicates withautomation control devices via WSD technology.

Alternatively or additionally, the WSD technology may be implementedusing Device Profile for Web Services (DPWS). The DPWS may be used todefine how various devices may be able to use Web Services inconjunction with the convergence solution noted above. The DPWS furthermay allow and/or ensure interoperability between the various devices 102and the clients 104 and the like. Moreover, the DPWS may allow forsupport of resource constrained devices within the convergence solutionshown in FIG. 1. One benefit of DPWS is its ability to enable device andservice discovery within the convergence solution of FIG. 1. The DPWSmay allow for and support rich eventing, an end point, and may be builton standards and WS specifications. More specifically, the end point mayprovide device/host metadata. Additionally, the DPWS specifications mayinclude HTTP, WSDL, SOAP, WS-Discovery, WS-Addressing, WS-Eventing,WS-metadata, transfer, and the like.

FIG. 2 schematically shows the Web Services for Devices (WSD) Stack foruse in the convergence solution of FIG. 1, constructed according to theprinciples in the invention. The WSD stack as referenced herein refersto the protocol architecture. In particular, FIG. 2 shows the WSD Stack200. The WSD stack 200 of the invention is a particular automationsoftware implementation of a Web Services computer networking protocolsuite. The individual protocols are designed with a single purpose inmind. Because each protocol module may only communicate with two others,the modules are commonly imagined as layers in a stack of protocols. Thelowest protocol always deals with “low-level,” physical interaction ofthe hardware. Every higher layer adds more features. As described ingreater detail below, the WSD Stack 200 allows and enables the discoveryof devices in a network, such as the convergence solution of FIG. 1 andthe devices on the network in a light weight, simple fashion. Using theWSD Stack 200, a device 102 in the network is able to send a message todetermine what services are available enabling discovery of the device102.

The WSD Stack 200 is the software that may be used to process protocols.The WSD Stack 200 is required to use a specific set of protocols. Inparticular, the WSD Stack 200 leverages Web Services for Devices tocreate a powerful, extensible system that may communicate with a widevariety of devices 102 described in greater detail above. As shown inFIG. 2, the WSD Stack is shown schematically at a high level. The WSDStack 200 in FIG. 2 shows the communication to and from clients 104 atthe top of the diagram via a logical interface and the various hardwaredevices 102 arranged at the very bottom of FIG. 2.

The logical interface initially communicates with and through the WSDStack 200 via a Hyper Text Transfer Protocol (HTTP) or a User DatagramProtocol (UDP) as indicated by reference numeral 201. The HTTP enablesdata transfer and display of web pages and the like as is well known inthe art. The UDP enables a direct way to send and receive datagrams onan IP network as is well known in the art. Accordingly, the clients 104interface via the logical interface through one or both of the HTTP andUDP layers 201 to a service provider 202. For example, communicationfrom the client 104 to the service provider 202 may be via the HTTP orUDP information and the communication may be contained in SOAP packets.

The service provider 202 may be configured as a large, generic host forweb services. The service provider 202 may host one or more components205 therein. A component 205 may have the ability to host multipleservices. However, the component 205 may limit the relationship betweena service and a device to a one-to-one relationship.

A further part of the component 205 is the web service 203. The webservice 203 exists for each device 204. The web service 203 may beconfigured as a generic web service based on the device category. Forexample, a thermostat has a corresponding web service based on the HVACcategory for example only.

Each web service 203 may be configured with a device bridge 204. Thedevice bridge 204 may be configured to essentially translate commands bythe physical devices 102. Accordingly, each device bridge 204 may bespecific to the specific make of the physical device 102.

The service provider 203 may further include a controller 206. Thecontroller 206 may be arranged to communicate with the devices 102. Thecontroller 206 may be configured to have a ratio of one controller percomponent 205. The controller 206 may include the ability to sendfeedback from the devices 102 to the component 204. The component 204may then route the feedback to the appropriate web service 203.Accordingly, this arrangement provides the ability for feedback from thedevices 102 to various clients 104.

The service provider 202 next may communicate to the various physicaldevices 102 via one or more of a plurality of different communicationsprotocol 207. In particular, the communications protocol with thedevices 102 may include any type of native or proprietary format. Suchnative or proprietary formats may be sent via Hyper Text TransferProtocol (HTTP), transmission control protocol (TCP), user datagramprotocol (UDP), or serial protocols. The TCP enables two hosts toconnect. The serial protocol provides one or two way serialcommunication as is well known in the art.

Accordingly, the WSD Stack 200 creates a powerful and extensible systembased on web services for devices. Moreover, the WSD Stack 200 maycommunicate with a wide variety of devices 102 as discussed in detailwith respect to FIG. 1 above. Using the WSD Stack 200 allows networkcomponents to become “black box” components. This allows the variousclients 104 and devices 102 to communicate in a clearly defined waywithout needing to know how they are accomplishing their various tasks.Using the WSD Stack 200 allows components to be implemented on anyapplication running on any platform and written in any language. Inessence, when the WSD Stack 200 is implemented, the network location andcommunications are handled by the platform, allowing applicationdevelopers to focus solely on application problems. It should be notedthat various modifications to the WSD Stack 200 are contemplated by theinvention.

FIG. 3 shows a device life cycle operating according to the principlesof the invention. In particular, FIG. 3 shows the various portions ofthe life cycle of a device networking using the WSD Stack 200 describedabove and shown in FIG. 2 in a device 102 as shown in FIG. 1 above.Initially, as shown in FIG. 3, the first step in a device 102 in itslife cycle on the network is discovery 302. Discovery 302 as used inconjunction with the WSD Stack 200 may use the WS-Discoveryspecification. The WS-Discovery specification may include multicastannouncements, multicast query requests such as probe and probe match,and unicast responses. In this regard, a device 102 may probe a client104 using the discovery networking life cycle 302 to receive a probematch from the client 104. In this regard, discovery of the device 102by one or more clients 104 is straight forward and essentiallyautomatic. More specifically, a device 102 may announce its presence asit is connected to the network 12. This announcement may be through asending out of a hello or bye message by device 102 on to the network12. Additionally, the device 102 may respond to a client 104 requestincluding various probe and resolve type requests. A probe request mayinclude the ability to identify a device or service within the client104 or device 102. The resolve request may include the ability to locatea device 102 or service end point. The result is the ability to get orobtain information via metadata exchange during the discovery 302process.

The next step in the networking life cycle of the WSD Stack 200 processincludes the step of description 304. The step of description 304 mayinclude a metadata exchange. This metadata exchange may be a response toa “get request.” The description step 304 may thus include theWS-Metadata exchange protocol and may moreover include the WSDL orSOAP/XML information exchange. The WSDL (Web Services DescriptionLanguage) may be used in combination with the SOAP and XML schema toprovide web services. A device connecting to the network 12 may read theWSDL to determine what functions are available on the network 12,clients 104 and the like. The SOAP (Simple Object Access Protocol) is aprotocol that may be used for exchanging XML based messages over thenetwork 12.

The next step in the networking life cycle shown in FIG. 3 is the stepof control 306. In the step of control 306, control over a device 102may be exercised by sending messages to the device 102 and/or serviceshosted by the device 102. The control 306 may be defined by the WSDL andXML schema. This definition of control 306 may ensure a common base linefor interoperability.

Finally, the last step in the networking life cycle shown in FIG. 3 isthe step of eventing 308. The eventing step 308 may include the WSDStack 200 web service-eventing and may again use the SOAP/XML schema. Inparticular, the eventing 308 may allow for a rich eventing model. Thismodel may allow for detailed events through WSDL. The eventing 308 mayallow a client to subscribe to various events. Moreover, the eventing308 may allow for the device 102 to push events to the clients 104.

Shown in FIG. 4, the convergence solution may further include a controlpanel 36 configured to interact with the network 12 in order to providethe clients 104 (e.g., TV 30, PC 32, control panel 36 and the like)connected thereto with the capability to control the convergencesolution. For example, the control panel 36 may provide a graphical userinterface (GUI) to the clients 104 connected thereto (e.g., television30, PC 32, PDA 34 or remote control device 39).

In an exemplary embodiment, the network 12 may communicate via InternetProtocol via a wired and/or wireless Ethernet network. The devices 102and clients 104 may communicate via a variety of native protocols suchas RS-232, RS-485, USB, WSD, wireless mesh network (e.g. Z-Wave,ZigBee), IP, or UPnP, but not necessarily limited to those protocols.Exemplary control devices which may be implemented to monitor and/orcontrol the automation devices/functions may include a TV GUI, infraredor radio frequency remote control, personal computer (PC), web-enabledtablet, PDA, mobile phone or other device, to name only a few examples.

In an embodiment, the control panel 36 may be a touch screen device asshown in FIGS. 5A and 5B. The touch screen device 36 may include adisplay panel 502. The display panel 502 may be an LCD type display.However, any other type of display technology is contemplated for use asthe display 502. Also, the touch screen device 36 may include a housing522 that may include key holes and keys to interact with each other andto hold the touch screen device 36 in place without any other mechanicalfasteners (not shown). Additionally, the touch screen device 36 mayinclude an audio line out type of arrangement including speakers 510,512 to provide audio output for the touch screen device 36. Moreover,the touch screen device 36 may include a microphone 524 for receivingaudio input for intercom functions and the like. It is contemplated thatthe touch screen device 36 may be voice activated to receive voicecommands/inputs and be able to operate in response thereto.

The touch screen device 36, because it is web based, may require only anwired or wireless Ethernet connection as shown in FIG. 4 and a powerconnection. For example, the Ethernet connection may be a typicalRJ45-type connection, and the power connection may be a 14-16 gauge-typewire pair connecting to a DC power source 12 volts, and the like. Thetouch screen device 36 may be based on a notebook processor, forexample, an Intel™ Pentium M-type processor or Core™ Duo Processor. Thetouch screen device 36 may include a touch sensor arrangement overlaidon the display panel 502. Moreover, the touch screen device 502 may bearranged with a plurality of USB type connections or the like. The touchscreen device 36 may also be configured to have a virtual QWERTY typekeyboard that may be virtually arranged on the display panel 502 forentry of alpha-numeric characters by touching areas of the display 502.

The touch screen device 36 may further be provided with an IR (infrared)receiver for receiving an IR signal from a remote control device, forexample, the remote 39 in FIG. 4, to control the touch screen device 36.The IR receiver may be used for other functions as well. Also, the touchscreen device 36 may include a photocell sensor, which may be used tosense ambient light to control the display brightness of the displaypanel 502 and/or automatically adjust the ambient light level in a room.The photocell may also be used for other functions as well.

In FIG. 5B, the touch screen device 36 may have a rear compartment 530to house components including a CPU board, base board and hard drive.Additional components may be also contained in the rear compartment 530such as a blower fan, heat-sink, fan power jack and fan power cable. Theblower fan may be implemented as to be dynamically controlled based oninternal temperature. The rear compartment 530 may have exhaust openingfor directing the exhaust air from the squirrel cage blower fan.

In FIG. 6, the touch screen device 36 may include a plurality of hotspots 504, 508, 518, 514, and 520, which may be used for command orinput from a user by touching that part of the housing 522. The hotspots504, 508, 518, 514, and 520 may be capacitive sensing. However, any typeof touch sensitive technology is contemplated for use with theinvention. Each of these hotspots 504, 508, 518, 514, and 520 may beassigned with a particular feature, for example, turning on the lights,turning on a stereo, turning on the television and the like.Additionally, the touch screen device 36 may include slider areas 506,516 along the sides thereof. Again, these slider areas 506, 516 may usea capacitive type sensing mechanism to sense a sliding user input.Sliding a finger, for example, up or down the areas 506, 516 may providean increasing or decreasing actuation of a particular home automationcomponent such as lights or audio volume. Furthermore, the display panel502 may include a touch sensitive capacitive overlay which allows a userto touch various virtual buttons that are formed on the surface of thedisplay panel 502.

As mentioned above, once the touch screen device 36 is connected to thenetwork 12, the touch screen device 36 may be used to control thedevices 102 of the convergence and automation system. For example, thetouch screen device 36 that runs on the PC based media environment(e.g., Microsoft Media Center™ environment), the user may use the touchscreen device 36 to listen to music, watch and record television, enjoyfamily photographs and home movies, as well as adjust the lighting,secure the home, adjust the temperature, distribute music throughout thehouse, check surveillance cameras and the like. For example, FIGS. 7A,7B and 7C show screen capture images of the weather-related contentsdisplayed on the touch screen device 36. In case the user wants to knowthe current temperature, he or she may simply navigate the menudisplayed on the screen of the touch screen device 36. Particularly,FIG. 7A shows a start menu where the user can select one of thecategories such as “My TV,” “MY Music,” “Radio,” “My Home,” “MoreProgramming,” “Settings,” and the like. To access the informationrelated to weather, the user may select “My Home” by either touching theportion of the touch sensor arrangement overlaid on the “My Home” textor activating the hotspots 504, 508, 518, 514, and 520 and/or sliderareas 506, 516, programmed for such as mentioned above. Depending on theuser's navigation, the touch screen device 36 may display the currenttemperature of the house as shown in FIG. 7B or the weather forecast asshown in FIG. 7C which may be obtained from the internet 14.

As mentioned above, the touch screen device 36 allows the user tocontrol the devices 102. For example, FIGS. 8A and 8B show screencapture images of the lighting control-related contents displayed on thetouch screen device 36. Particularly, FIG. 8A shows a lighting menuwhere the user can select any lighting device in the house foractivation or adjustment. FIG. 8B shows that the rear overhead lights inthe living room have been selected and the user may select the lightlevel of the selected lighting device using the touch sensor arrangementor activating the hotspots 504, 508, 518, 514, and 520 and/or sliderareas 506, 516.

The touch screen device 36 may also be used to control media devices.For example, FIG. 9A shows a TV programming guide displayed on the touchscreen device 36, which allows the user to select a TV program to watchor record. As shown in FIG. 9B, the touch screen device 36 may beconfigured to show multiple channels of the same categories such asnews, sports, movies and the like, and play previously recorded programsat any location where the touch screen device 36 is installed.Similarly, the touch screen device 36 may be used to search and playmusic files and adjust the volume and/or change speaker and/or equalizersetups, as shown in FIG. 9C. Additionally, the touch screen device 36may be used to set, change, unlock the security system 28 as shown inFIG. 10A, watch feed from multiple surveillance cameras as shown in FIG.10B, and open or close the shades in the house as shown in FIG. 10C.

In accordance with various embodiments of the invention, the methodsdescribed herein are intended for operation with dedicated hardwareimplementations including, but not limited to, semiconductors,application specific integrated circuits, programmable logic arrays, andother hardware devices constructed to implement the methods and modulesdescribed herein. Moreover, various embodiments of the inventiondescribed herein are intended for operation with as software programsrunning on a computer processor. Furthermore, alternative softwareimplementations including, but not limited to, distributed processing orcomponent/object distributed processing, parallel processing, virtualmachine processing, any future enhancements, or any future protocol canalso be used to implement the methods described herein.

It should also be noted that the software implementations of theinvention as described herein are optionally stored on a tangiblestorage medium, such as: a magnetic medium such as a disk or tape; amagneto-optical or optical medium such as a disk; or a solid statemedium such as a memory card or other package that houses one or moreread-only (non-volatile) memories, random access memories, or otherre-writable (volatile) memories. A digital file attachment to email orother self-contained information archive or set of archives isconsidered a distribution medium equivalent to a tangible storagemedium. Accordingly, the invention is considered to include a tangiblestorage medium or distribution medium, as listed herein and includingart-recognized equivalents and successor media, in which the softwareimplementations herein are stored.

While the invention has been described in terms of exemplaryembodiments, those skilled in the art will recognize that the inventioncan be practiced with modifications in the spirit and scope of theappended claims. These examples given above are merely illustrative andare not meant to be an exhaustive list of all possible designs,embodiments, applications or modifications of the invention.

1. A process of operating an automation system in a Web Serviceenvironment, comprising steps of: providing at least one client and atleast one device, the at least one client and the at least one deviceconfigured with a web services for devices stack protocol; connecting anetwork comprising at least one server with the web services for devicesto the at least one client and the at least one device; connecting atouch screen device as another at least one client to the network, thetouch screen device implemented with a user interface for controllingthe at least one device; and transmitting automation-based control andcommunication between the at least one client and at least one device,wherein the at least one device comprises one of an audio system, avideo system, an intercom system, a lighting system, a security system,a link, and a HVAC system.
 2. The process according to claim 1 whereinthe at least one client comprises one of a TV, a personal computer, apersonal digital assistant, and a game controller.
 3. The processaccording to claim 1 further comprising the step of receiving a userinput to the touch screen device through at least one of hotspotarranged on a front surface of a touch screen housing configured toactivate a predetermined function upon being touched; and at least oneslider area arranged on an edge portion of the housing configured toprovide increasing or decreasing activation of a predetermined functionresponsive to a sliding touch.
 4. The process according to claim 1further comprising the step of generating audio from the touch screendevice with at least one speaker.
 5. The process according to claim 1further comprising the step of at least one of: receiving IR input tothe touch screen device through an IR receiver; and sensing light in thetouch screen device with a photocell sensor.
 6. The process according toclaim 1 wherein the web services for devices stack protocol comprises: aservices tier that provides communication via at least one of HTTP andUDP wherein the communication via HTTP and UDP comprises informationcontained in SOAP packets; and a logical interface with the at least oneclient, and the web services for devices stack protocol comprises a webservice for each at least one device, wherein the web services fordevices stack protocol comprises a service provider configured as ageneric host for web services.
 7. The process according to claim 1wherein the web services for devices stack protocol further comprisesone of a component configured to host multiple services, and acontroller configured to communicate with the at least one device andwherein the web services for devices stack protocol further comprises adevice bridge configured to translate commands for the devices.
 8. Amachine-readable medium comprising instructions stored therewith, which,when executed by a processor cause the processor to establish anautomation system in a Web Service environment, the machine-reachablemedium comprising: instructions for providing automation-based controland communication between at least one client and at least one device,the at least one client and the at least one device configured with aweb services for devices stack protocol configured to the at least oneclient and at least one device; instructions for configuring a networkcomprising at least one server to be connected to the at least oneclient and the at least one device with the web services for devices;and instructions for coupling a touch screen device as another at leastone client to the network and configured to provide the touch screendevice coupled thereto with a user interface for controlling thedevices, wherein the at least one device comprises an audio system, avideo system, an intercom system, a lighting system, a security system,a link, and a HVAC system.
 9. The machine-readable medium according toclaim 8 wherein the at least one client further comprises one of a TV, apersonal computer, a personal digital assistant, and a game controller.10. The machine-readable medium according to claim 8 further comprisinginstructions for generating audio from the touch screen device with atleast one speaker.
 11. The machine-readable medium according to claim 8further comprising instructions for receiving IR input to the touchscreen device through an IR receiver.
 12. The machine-readable mediumaccording to claim 8 further comprising instructions for sensing lightin the touch screen device with a photocell sensor.
 13. Themachine-readable medium according to claim 8 wherein the web servicesfor devices stack protocol comprises: a services tier that providescommunication via at least one of HTTP and UDP wherein the communicationvia HTTP and UDP comprises information contained in SOAP packets; and alogical interface with the at least one client, and the web services fordevices stack protocol comprises a web service for each at least onedevice.
 14. The machine-readable medium according to claim 8 wherein thecontroller is configured to send feedback from the at least one deviceto the at least one client.
 15. An automation system operating in a WebService for Devices environment, comprising: at least one client and atleast one device, the at least one client and the at least one deviceconfigured with a web services for devices stack protocol configured toprovide automation-based control and communication between the at leastone client and at least one device; a network comprising at least oneserver configured to be connected to the at least one client and the atleast one device with the web services for devices; and a touch screendevice coupled to the network as another at least one client to providea user interface to control the at least one device, wherein the atleast one client further comprises one of a TV, a personal computer, apersonal digital assistant, and a game controller and the at least onedevice comprises an audio system, a video system, an intercom system, alighting system, a security system, a link, and a HVAC system.
 16. Theautomation system of claim 15, wherein the touch screen devicecomprises: a display panel; a housing holding the display panel; and arear compartment arranged on a rear surface of the display panel andcontaining components for driving the display panel.
 17. The automationsystem of claim 15, wherein the housing comprising: at least one hotspotarranged on a front surface of the housing configured to activate apredetermined function upon being pushed; and at least one slider areaarranged on an edge portion of the housing configured to provideincreasing or decreasing activation of a predetermined function.
 18. Theautomation system of claim 15, wherein the touch screen device furthercomprises at least one speaker.
 19. The automation system of claim 15,wherein the touch screen device further comprises an IR receiver. 20.The automation system of claim 15, wherein the touch screen devicefurther comprises a photocell sensor.